The Azure Static Web Apps deployment workflow was triggering on both pull request events and pushes to main, causing premature deployments before copilot agent changes were finalized and merged.

Problem

Previously, the workflow deployed the app in two scenarios:

1. During PR review - When PRs were opened, synchronized, or reopened (before changes were finalized)
2. After merge - When code was pushed to main branch

This meant incomplete changes were being deployed during the PR review process, before the copilot agent had completed its work and the changes were properly reviewed and merged.

Solution

Modified the workflow to only deploy when code is pushed to the main branch:

# Before: Triggered on both PR events and push to main
on:
  push:
    branches: [main]
  pull_request:
    types: [opened, synchronize, reopened, closed]
    branches: [main]

# After: Only triggers on push to main
on:
  push:
    branches: [main]

Changes Made

• ✅ Removed pull_request triggers from workflow events
• ✅ Removed conditional logic for PR vs push events
• ✅ Removed close_pull_request_job that handled PR cleanup
• ✅ Simplified workflow to only run on push to main branch

Result

Deployment to Azure Static Web Apps now only happens after code is merged to the main branch, ensuring that all copilot agent changes are included in the deployed version. The workflow is simpler, more predictable, and prevents deployment of incomplete changes during the PR review process.

Fixes #7.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.